You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Branches and PRs show up correctly on in the web/browser view:
But when inspecting the same ticket inside the extension no branches show up. The only option available for "Start work" is creating a brand new branch for this work. Even branches creating via that mechanism do not get recognised by the extension.
Expected behavior
The same branches that show up associated with the issue in web view are recognised in the vscode extension.
Environment and Version (please complete the following information):
Atlassian Plugin Version (3.4.25)
Visual Studio Code Version (1.99.0)
Is this a local or cloud environment? (Local)
If Local, OS (macOS)
Additional context
This is using Azure Repos connected with our Jira setup.
The text was updated successfully, but these errors were encountered:
If I understand correctly, you'd like to pull the branch that has been already created for (or associated to) the issue, and continue working with it from vscode.
I believe this scenario is not supported yet, but it does sound a great idea.
Although, while this works well if the associated branch is your workspace's repository, I wonder what the extension should do if the branch is not from the same repo.
Describe the bug
Branches and PRs show up correctly on in the web/browser view:
But when inspecting the same ticket inside the extension no branches show up. The only option available for "Start work" is creating a brand new branch for this work. Even branches creating via that mechanism do not get recognised by the extension.
Expected behavior
The same branches that show up associated with the issue in web view are recognised in the vscode extension.
Environment and Version (please complete the following information):
Additional context
This is using Azure Repos connected with our Jira setup.
The text was updated successfully, but these errors were encountered: